Skip to content

cli: Add --rekor-version to sign arguments #1471

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

jku
Copy link
Member

@jku jku commented Jul 22, 2025

This adds a CLI option that should not be needed... but it could be handy if

  • SigningConfig already contains rekor v2 (and still contains a v1 instance)
  • user for some reason does not want rekor v2 entries in the bundle

This option only does anything if there are multiple Rekor versions listed in SigningConfig.

The test is changed since the "ANY" selector is now considered to not be
an error if there are 0 services:

  • This is not a problem since for both TSAs and tlogs we have a check
    that there is at least one service
  • This improves the error message when --rekor-version is used with
    a version that is not found in signingconfig

@jku jku force-pushed the add-rekor-version-option branch 3 times, most recently from aa1cb9e to a86bcf7 Compare July 22, 2025 11:59
@jku jku force-pushed the add-rekor-version-option branch from a86bcf7 to 55c8911 Compare July 23, 2025 13:47
@jku
Copy link
Member Author

jku commented Jul 23, 2025

I'm filing a separate issue about testing the bundle compatibility -- choosing the rekor version is one thing but there are other related changes in the bundle we produce (like TSA timestamps) that could affect compatibility

jku added 3 commits July 23, 2025 17:48
This should not be needed... but it could be handy if
* SigningConfig already contains rekor v2
* user for some reason does not want rekor v2 entries in
  the bundle

This option only does anything if there are multiple Rekor versions
listed in SigningConfig.

The test is changed since the "ANY" selector is now considered to not be
an error if there are 0 services:
* This is not a problem since for both TSAs and tlogs we have a check
  that there is at least one service
* This improves the error message when --rekor-version is used with
  a version that is not found in signingconfig

Signed-off-by: Jussi Kukkonen <[email protected]>
Signed-off-by: Jussi Kukkonen <[email protected]>
Avoid saying "default: None", mention the valid values instead.

Signed-off-by: Jussi Kukkonen <[email protected]>
@jku jku force-pushed the add-rekor-version-option branch from 55c8911 to dc21376 Compare July 23, 2025 14:49
@jku
Copy link
Member Author

jku commented Jul 23, 2025

I'm keeping this a draft until I'm confident I know how #1474 looks like

@jku jku force-pushed the add-rekor-version-option branch from 25be8c6 to b36e65b Compare August 15, 2025 12:14
@jku
Copy link
Member Author

jku commented Aug 15, 2025

Marking ready for review: I'm still not sure if this is actually useful but happy to include (and improve) it if others feel like it's useful.

sigstore-python 3.6.5 correctly verifies a signature bundle created with sigstore-python from this branch if --rekor-version 1 is used.

@jku jku marked this pull request as ready for review August 15, 2025 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants